-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement pipectl migrate with get then set at pipectl side #5506
Conversation
Signed-off-by: Shinnosuke Sawada-Dazai <[email protected]>
Signed-off-by: Shinnosuke Sawada-Dazai <[email protected]>
Signed-off-by: Shinnosuke Sawada-Dazai <[email protected]>
Signed-off-by: Shinnosuke Sawada-Dazai <[email protected]>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #5506 +/- ##
==========================================
- Coverage 26.29% 26.27% -0.02%
==========================================
Files 464 464
Lines 49626 49635 +9
==========================================
- Hits 13047 13043 -4
- Misses 35546 35558 +12
- Partials 1033 1034 +1 ☔ View full report in Codecov by Sentry. |
I tested on local, and got the output below.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good.
Please link a task management Issue for this PR later.
What this PR does:
This PR modifies the pipectl migrate database command to get the platformProvider and set the deployTargets on client-side operation, not server-side operation.
Why we need it:
The current implementation needs to change when we have a use case that needs to migrate data again, but changing the behavior of the existing RPC is not a good option.
The pipectl side can be considered a script to migrate, and it's not bad to change behavior depending on versions. So I moved the operation to the pipectl side.
Which issue(s) this PR fixes:
Part of #5252
Does this PR introduce a user-facing change?: No